Bristol City Council
Tree preservation zone
There is a problem
- 365 entries with tree-protection-order field must match the reference field in the tree protection order dataset
Cote, New Cote And Cote Paddock Cote Drive Bristol BS9 3UR
- reference
- ICS3HBDNBB000
- name
- Cote, New Cote And Cote Paddock Cote Drive Bristol BS9 3UR
- tree-preservation-order
- 074
- tree-preservation-zone-type
- group
- geometry
- MULTIPOLYGON (((-2.619858 51.481858,-2.619962 51.481908,-2.619998 51.481910,-2.620030 51.481897,-2.620036 51.481879,-2.619987 51.481845,-2.619916 51.481834,-2.619890 51.481820,-2.619886 51.481787,-2.619893 51.481771,-2.619979 51.481749,-2.620002 51.481714,-2.619940 51.481692,-2.619882 51.481683,-2.619804 51.481637,-2.619745 51.481587,-2.619573 51.481527,-2.619150 51.481302,-2.618982 51.481231,-2.618981 51.481189,-2.618818 51.481063,-2.618814 51.480998,-2.618706 51.480918,-2.618687 51.480886,-2.618530 51.480767,-2.618465 51.480739,-2.618345 51.480705,-2.618306 51.480685,-2.618048 51.480634,-2.617935 51.480635,-2.617925 51.480667,-2.617952 51.480722,-2.618017 51.480747,-2.618043 51.480782,-2.618461 51.480894,-2.618523 51.480930,-2.618601 51.481032,-2.618624 51.481042,-2.618641 51.481061,-2.618679 51.481064,-2.618705 51.481056,-2.618712 51.481068,-2.618699 51.481092,-2.618713 51.481133,-2.618761 51.481163,-2.618787 51.481165,-2.618846 51.481213,-2.618872 51.481249,-2.618944 51.481300,-2.618999 51.481307,-2.619028 51.481346,-2.619019 51.481372,-2.619075 51.481442,-2.619147 51.481492,-2.619462 51.481669,-2.619569 51.481684,-2.619725 51.481792,-2.619858 51.481858)))
- point
- POINT (-2.619007 51.481246)
- notes
- MATURE GROUP OF LIME,BEECH,SYCAMORE,ELM
- organisation
- entry-date
- 2005-03-03
- start-date
- 2005-03-03
- end-date
How to fix this issue
Your dataset is missing the tree-preservation-order column.
The Tree preservation zone guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that covers this zone.
How to improve Bristol City Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL